Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added E2E tests using the SQLiteKIM #529

Conversation

MattDavis00
Copy link
Member

Runs the current E2E all_providers::normal tests. Doesn't run multitenancy etc.

Closes #516

Signed-off-by: Matt Davis matt.davis@arm.com

Closes parallaxsecond#516

Signed-off-by: Matt Davis <matt.davis@arm.com>
@MattDavis00 MattDavis00 requested a review from a team as a code owner September 21, 2021 14:43
Copy link
Member

@hug-dev hug-dev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good for me! I think the important point in my comment is about adding some persistence test for the SQL KIM.

Also thinking more and more that our test script is getting more and more complicated and is all in one line of bash... We might want at some point to switch to something more maintainable and scalable.

wait_for_service

echo "Execute all-providers sqlite-kim normal tests"
RUST_BACKTRACE=1 cargo test $TEST_FEATURES --manifest-path ./e2e_tests/Cargo.toml all_providers::normal
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am wondering, if we are going to promote the SQL KIM as the default KIM from now on, if we should change all config files to use the SQL KIM and add that if case for the legacy KIM.

Also, we might need stability/persistence tests for it: that old mappings stored with that KIM can still be read in current PRs. Check the "per provider key mappings tests" here

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I was also wondering whether we should make it the default. The reason it is currently only the subset of tests (all_providers::normal) is that quite a few of the E2E tests currently rely on the fact that the OnDiskKIM is able to store keys with the same name in different providers. Tests that rely on this logic obviously fail. Quite a few of the E2E tests would therefore need refactoring to account for this, hence why I went with this approach for now 😅 better to have some E2E tests that none.

As for stability tests I already have an issue tracking this here that hopefully somebody will pick up, or me when I'm back.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh nice that you already thought about stability in an issue 👍
Understand about the refactoring needed for the tests. Could you please open an extra-issue about "Making the SQL KIM the default" to track what needs to be done for it?
I am fine to merge this PR then.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will do

@MattDavis00 MattDavis00 merged commit 28dd22d into parallaxsecond:feature-sqlite-kim Sep 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants